-
Couldn't load subscription status.
- Fork 4
Add initial code imported from the SDK #7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
llucax
commented
Jun 13, 2024
- Import implementation from the SDK v1.0.0rc601
- Add an introduction and example to the package documentation
- Include the package documentation in the website home
- Add a link to the documentation in the README
| """Types for holding quantities with units.""" | ||
| """Types for holding quantities with units. | ||
| This library provide types for holding quantities with units. The main goal is to avoid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe remove the first sentence as it is equal to the headline
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a title/summary, like with git commits. There are some options or places where only the summary line is shown.
The only difference with the SDK is the files are split to have one per quantity type, to have more manageable files. Also `_NoDefaultConstructible` was renamed to `NoDefaultConstructible`, as it is used outside the module it is defined in (`_quantity.py`). It is not exported in `__init__.py` though. In the future it should probably be moved to some core library. The tests are also imported from the SDK but kept in one file, as there are many tests that use multiple quantity types to compose them. Signed-off-by: Leandro Lucarella <[email protected]>
Signed-off-by: Leandro Lucarella <[email protected]>
Signed-off-by: Leandro Lucarella <[email protected]>
Signed-off-by: Leandro Lucarella <[email protected]>
We'll release v1.0.0 soon, so we should update the edit URL to point to the v1.x.x branch instead of the v0.x.x branch. Signed-off-by: Leandro Lucarella <[email protected]>
|
I updated the branch to v1.x.x to follow the suggestion in frequenz-floss/frequenz-sdk-python#852. I think this is mature enough to go with a v1.0.0. If we want to make breaking changes we can start a new v2.x.x branch, but it will make us asses the cost-benefit from doing that and avoid cheap breaking changes... |
Signed-off-by: Leandro Lucarella <[email protected]>
|
Added release notes assuming v1.0.0 will be released after this is merged. |